feat(mcp_catalog): add 7 remote streamable-http servers#2894
Merged
Conversation
docker-agent
left a comment
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🟢 APPROVE
7 new streamable-http MCP server entries reviewed (cloudflare, figma, microchip, neon, paypal, supabase, tally).
Checks passed:
- ✅
countfield: bumped from 44 → 51, matches exactly 51 server entries in the file - ✅ All 7 new entries have required fields (
id,title,description,url,transport,auth) - ✅
transportvalues arestreamable-httpfor all new entries (consistent with PR intent) - ✅
authvalues are valid (oauthfor 6 entries,nonefor microchip) - ✅ All URLs are well-formed HTTPS endpoints
- ✅ No duplicate IDs introduced
- ✅ Entries are correctly inserted in alphabetical order by
id - ✅ No breaking schema changes
No bugs found. The changes are clean and consistent with the existing catalog conventions.
dgageot
force-pushed
the
feat/mcp-catalog-add-servers
branch
from
30490cb to
5daebe6
Compare
trungutt
approved these changes
May 26, 2026
aheritier
added
area/mcp
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
mcp_catalogtoolset embeds a curated snapshot of remote streamable-http MCP servers from the Docker MCP Catalog. This PR extends that snapshot with 7 newly verified servers.Each candidate was discovered by web research and then probed against the live endpoint with a real MCP
initializerequest to confirm streamable-http transport. The probe sentAccept: application/json, text/event-streamand verified either a 200 OK response with a validinitializereply, or a 401 with validoauth-protected-resourcemetadata in theWWW-Authenticate: Bearerchallenge.All OAuth servers expose the standard
WWW-Authenticate: Bearerchallenge withresource_metadatadiscovery, so docker-agent's existing OAuth + Dynamic Client Registration plumbing should work without per-server configuration. This mirrors the same path already taken by Linear, Notion, and Atlassian.The catalog
countfield was bumped from 44 to 51 and entries were re-sorted by id to match the existing convention. Tests pass (go test ./pkg/tools/builtin/mcpcatalog/...is green) and linting reports 0 issues (task lint).Note: this is a snapshot of the live catalog at https://desktop.docker.com/mcp/catalog/v3/catalog.json. Long-term, these servers should be proposed upstream so the live-fetched catalog stays consistent across docker-agent releases.